[Common] TrackTuner: fix mean shift.#17091
Open
mfaggin wants to merge 1 commit into
Open
Conversation
mfaggin
requested review from
a team,
alibuild,
ddobrigk,
dsekihat,
iarsene,
jgrosseo and
ktf
as code owners
July 16, 2026 12:17
|
O2 linter results: ❌ 27 errors, |
Collaborator
|
Error while checking build/O2Physics/code-check for da85440 at 2026-07-16 14:28: Full log here. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes a conceptual mistake in the dca mean shift applied with the TrackTuner (with no impact for current analyses, see later).
From the PR #7009 the dca correction is the following:
In particular, that PR introduced the subtraction of the dcaMC mean from the reco dca in MC, in order to center it at 0 when computing the residual to the generated y parameter, i.e. in the calculation of the dca resolution term. This operation already centers the reconstructed dca in MC to 0, i.e. the
-<dcaXYMC_reco>term in the 3rd row is a leftover. In this PR we remove this term, ending up with the following formula:In particular, this formula now provides a robust correction, which in the ideal case of MC perfectly matching the data returns exactly the reconstructed dca in MC as it is.
The discussed issue is fixed with this PR. However, this should be totally transparent in analysis given that the dca mean in MC looks always at 0. Below some plots with some tests done on the pp reference HF MC
LHC25b4a6, showing the performance of the mean and sigma w/o the usage of the TrackTuner (black), with the usage of the TrackTuner as in O2Physics up to now (violet) and with the usage of the TrackTuner as fixed in this PR (green). As expected, the TrackTuner changes the mean and resolution of the DCA, but the fix in the TrackTuner mean shift of this PR does not have a big impact given that<dca_MC>=0(in other words: the violet and the green points coincide, even if the green are conceptually more correct).Mean:
Resolution:
Thanks @fchinu for spotting it.
Tagging also @arossi81 and @phymanshu for info